Skip to content

Conversation

@stainless-app
Copy link
Contributor

@stainless-app stainless-app bot commented Sep 5, 2025

Automated Release PR

0.11.1 (2025-09-06)

Full Changelog: v0.11.0...v0.11.1

Features

  • api: add pagination to the deployments endpoint (e5838f5)
  • api: pagination properties added to response (has_more, next_offset) (5f2329f)
  • api: update API spec with pagination headers (f64f55b)

Chores

  • internal: move mypy configurations to pyproject.toml file (4818d2d)
  • tests: simplify get_platform test (cd90a49)

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions


TL;DR

This release introduces pagination for the deployments.list() endpoint and moves the MyPy configuration into pyproject.toml.

Why we made these changes

Fetching a large number of deployments could be slow and lead to timeouts. Pagination allows clients to retrieve results in manageable chunks, improving the performance and reliability of the API for users with many deployments.

What changed?

  • Pagination:
    • The deployments.list() method now accepts limit and offset parameters.
    • The method returns a paginated object that includes has_more and next_offset properties for easier iteration.
    • Updated DeploymentListParams and DeploymentListResponse to support pagination.
  • Documentation:
    • Added a new "Pagination" section to the README.md with examples for both automatic and manual pagination.
  • Internal:
    • Consolidated project configuration by moving MyPy settings from mypy.ini (now deleted) to pyproject.toml.
    • Updated tests for the deployments resource to validate the new paginated response structure.

Description generated by Mesa. Update settings

@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 5, 2025

🧪 Testing

To try out this version of the SDK, run:

pip install 'https://pkg.stainless.com/s/kernel-python/cd90a498d24b1f4490583bec64e5e670eb725197/kernel-0.11.0-py3-none-any.whl'

Expires: Mon, 06 Oct 2025 03:56:33 GMT

Copy link

@mesa-dot-dev mesa-dot-dev bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Performed full review of 1bf1011...6c8bd29

Tip

⚡ Quick Actions

This review was generated by Mesa.

Actions:

Slash Commands:

  • /review - Request a full code review
  • /review latest - Review only changes since the last review
  • /describe - Generate PR description. This will update the PR body or issue comment depending on your configuration
  • /help - Get help with Mesa commands and configuration options

5 files reviewed | 1 comments | Review on Mesa | Edit Reviewer Settings

#
# We also exclude our `tests` as mypy doesn't always infer
# types correctly and Pyright will still catch any type errors.
exclude = ['src/kernel/_files.py', '_dev/.*.py', 'tests/.*']
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Medium Logic

The exclude pattern format has changed from regex format (^(src/kernel/_files\.py|_dev/.*\.py|tests/.*)$) to a simpler glob-like format (['src/kernel/_files.py', '_dev/.*.py', 'tests/.*']). While this may work, you should verify that mypy correctly interprets this new format, especially for the wildcard patterns like _dev/.*.py and tests/.*. The original regex format was more explicit about matching paths.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 6c8bd29 to 2252f04 Compare September 5, 2025 15:17
@stainless-app stainless-app bot changed the title release: 0.11.1 release: 0.12.0 Sep 5, 2025
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 2252f04 to 5867eab Compare September 5, 2025 15:17
@jarugupj jarugupj changed the title release: 0.12.0 release: 0.11.1 Sep 5, 2025
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 5, 2025

Release version edited manually

The Pull Request version has been manually set to 0.11.1 and will be used for the release.

If you instead want to use the version number 0.12.0 generated from conventional commits, just remove the label autorelease: custom version from this Pull Request.

@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 5867eab to 3fc176e Compare September 5, 2025 15:18
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 3fc176e to f872597 Compare September 5, 2025 15:19
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from f872597 to 97019bc Compare September 5, 2025 18:00
`nest_asyncio` is archived and broken on some platforms so it's
not worth keeping in our test suite.
@stainless-app stainless-app bot force-pushed the release-please--branches--main--changes--next branch from 97019bc to 0287597 Compare September 6, 2025 03:56
Copy link
Contributor

@masnwilliams masnwilliams left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@stainless-app stainless-app bot merged commit b63da5f into main Sep 9, 2025
7 checks passed
@stainless-app
Copy link
Contributor Author

stainless-app bot commented Sep 9, 2025

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants